Rfc 1265 Bgp
ثبت نشده
چکیده
This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 2. Introduction. The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol (BGP). This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This is the first of two reports on the BGP protocol. BGP is an inter-autonomous system routing protocol designed for the TCP/IP internets. Version 1 of the BGP protocol was published in RFC 1105. Since then BGP versions 2 and 3 have been developed. Version 2 was documented in RFC 1163. Version 3 is documented in [1]. The changes between versions 1, 2 and 3 are explained in Appendix 3 of [1]. Possible applications of BGP in the Internet are documented in [2]. The BGP protocol has been developed by the IWG/BGP Working Group of the Internet Engineering Task Force. We would like to express our deepest thanks to Guy Almes (Rice University) who was the previous chairman of the IWG Working Group. We also like to explicitly thank Bob Braden (ISI) and Bob Hinden (BBN) for the review of this document as well as their constructive and valuable comments. 4. Key features and algorithms of the BGP protocol. This section summarizes the key features and algorithms of the BGP protocol. BGP is an inter-autonomous system routing protocol; it is designed to be used between multiple autonomous systems. BGP assumes that routing within an autonomous system is done by an intra-autonomous system routing protocol. BGP does not make any assumptions BGP Working Group [Page 1]
منابع مشابه
Autonomous-System-Wide Unique BGP Identifier for BGP-4
To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only Autonomous-Systemwide (AS-wide) uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any b...
متن کاملRFC 4274 BGP - 4 Protocol Analysis January
The purpose of this report is to document how the requirements for publication of a routing protocol as an Internet Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report satisfies the requirement for "the second report", as described in Section 6.0 of RFC 1264. In order to fulfill the requirement, this report augments RFC 1774 and summarizes the key featur...
متن کاملRFC 4381 Security of BGP / MPLS IP VPNs February
This document analyses the security of the BGP/MPLS IP virtual private network (VPN) architecture that is described in RFC 4364, for the benefit of service providers and VPN users. The analysis shows that BGP/MPLS IP VPN networks can be as secure as traditional layer-2 VPN services using Asynchronous Transfer Mode (ATM) or Frame Relay. Behringer Informational [Page 1] RFC 4381 Security of BGP/M...
متن کاملRfc 4275 Bgp - 4 Mib
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document provides a survey of implementations of BGP-4 that support RFC 1657 MIB agents according to the BGP-4 v1 MIB specification.
متن کاملGraceful Restart Mechanism for BGP
This document describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined that would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finall...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 1991